-
Notifications
You must be signed in to change notification settings - Fork 4
Add integration test playbook. #4
Conversation
bdero
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a couple of tiny change requests, one to work around a bug in Ansible. I was able to complete the test playbook successfully though. :)
tests/integration.yml
Outdated
| wait_for: | ||
| path: "{{ LOAD_BALANCER_CERTS_DIR }}/{{ TEST_DOMAIN }}.pem" | ||
| timeout: 360 | ||
| - name: wait for haproxy to be restartet |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small typo: s/restartet/restarted
| - name: start pydoc as test backend on the server | ||
| command: nohup pydoc -p 5000 | ||
| async: 45 | ||
| poll: 0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So I think I ran into this bug with ansible==2.0.1.0 on this async task:
fatal: [haproxy-test.bdero.me]: FAILED! => {"changed": false, "failed": true, "msg": "The async task did not return valid JSON: No JSON object could be decoded"}
I was able to steer around the problem by appending become: False. Can you add it in here since escalating to root isn't necessary for this task anyway?
|
@bdero Thanks for you comments! The issues are fixed in the latest commit. |
|
👍
|
Testing instructions are included in the README.md file.